Monster Media 1996 #15

home *** CD-ROM | disk | FTP | other *** search

/ Monster Media 1996 #15 / Monster Media Number 15 (Monster Media)(July 1996).ISO / bbs_lord / lin_lord.zip / LINAPP.ZIP / POLICY.DOC < prev next >

Wrap

Text File | 1996-03-26 | 20KB | 412 lines

╔════════════════════════════════════════╗ ║ *** Linear Network Guidelines *** ║ ║ Last Update: March 25, 1996 ║ ╚════════════════════════════════════════╝ ╒══════════════════════════╕ │ Purpose of this Document │ ╘══════════════════════════╛ The purpose of this document is to lay down guidelines for which Linear Network will be operated and organized in order to make things run as smoothly and as efficiently as possible for all members. This Document will be changed as the network grows, to meet the members needs. ╒╤════════════════════════╤╕ ╘╡ What is Linear Network?╞╛ ╘════════════════════════╛ Linear Network is simple.. Lets Start with Webster: _ Lin.e.ar (Lin'e-ar),Adj. 1. of or in a line or lines. 2. Made of lines; making use of lines. 3. long and narrow. [<L, <linea Line] Networks are made up of lines (Phone lines) the more lines to connect the stronger the network. Linear Network is made up with these principles. Hoping that one day all parts of the globe will have knowledge of the Linear Net. ╒═══════════════════════════════╕ │ The Linear Network Structure. │ ╘═══════════════════════════════╛ Node -> Mail Hub -> Area Host -> The AMM To keep things simple Linear Network is broken down much the same as other nets. Above is an example of the network structure. It is also an example of how mail is passed through the network with the individual Node having the smallest responsibility and the Host having the largest responsibility. The Amm is the Automated Mail Machine that We use as a connecting Point. When you write mail or play a Game it will end up at the AMM, and be passed through to wherever it needs to go. The AMM is currently in Dallas Texas, and Has no BBS, per say, as it is set up just to pass files and mail for the members. ╓───────────────────╖ ║ Individual Nodes. ║ ╙───────────────────╜ The "Node" is what makes up the majority of the network. A node is basically just an individual bulletin board system. It is up to the Sysop of the individual Node to make sure that their users are following the rules of the echoes (no abusive behavior, no foul language, no illegal activities through the echoes, etc.) and make sure the games set up on his/her BBS is running smoothly. The Sysop of the individual Node can also help promote the net on his/her BBS and encourage his/her users to "check it out". The Best way of doing this is to Display the enclosed LINEAR.ANS & LINEAR.ASC. Nodes may be asked to pay a small fee to help support Long distance bills that are brought on by the Area Hosts. But on the most part it is Free to be a Node, as there NO set fee's for the Linear Network. ╓──────────────╖ ║ Mail Hubs ║ ╙──────────────╜ Nodes that send mail to several Nodes are called "Hubs". A Hub is a node with special key networking functions. Hubs are very important to the network structure because they do the bulk of the mail routing. A system with Hub status will be marked so in the nodelist with a flag "Hub". A 14,400 BPS or higher modem is minimum (it just helps to get the mail sent out faster) as well a Hub's BBS must have been up and running for at least six months prior to applying for hub status. The Hub's responsibilities are to make sure that All Nodes under them are on line and Getting there Mail and What ever *.TIC files that are being asked for (See LINEBONE.TXT) A Hub can get mail from one of two possible sources: 1) An Area Host, or 2) Directly from the Net Coordinator's BBS (emergencies only) It is the Hub's job to send out mail to its individual Nodes. If one of the individual Nodes is going to be "Down" for a short period of time, it is up to the Hub to put that system's mail on "Hold" until he/she is ready to resume operations. If the individual Node will be "Down" for an extended period of time, it is up to the Hub to notify the Area Host for that area so that the Node can be flagged as "Down" in the nodelist. Once the Node is back up and running, the same procedure will be followed in order to have the "Down" notation taken off the nodelist. A Hub is also responsible for sending any APP (applications for Linear Network membership) which they receive to their Area Host. The Hub will also notify his/her Area Host of any changes that need to be made in the nodelist for any of the individual Nodes under him/her. These APP files will need to be sent to his/her Area Host on Wednesday (by midnight) of each week. Application files received by the Area Host after Wednesday will be held and added to the following week's nodelist. A Hub must make available (for download and file requesting) the Linear Network application/information packet (LINAPP.ZIP) A Hub is responsible for helping set-up new Nodes under him/her. This is to include helping he/she get his/her message echoes set up properly, informing them how to do an Area fix, and to make sure that their information is right (correct net address in their origin line, correct information for the nodelist, messages in the right echoes, etc.). If the Hub is having any problems in helping the Node get set-up (modem won't connect, Node is using software unfamiliar to the Hub, etc.), the Hub will then contact the Area Host and he/she will try to help get things set up. Ideally each Hub will handle up to 10 individual Nodes. But if the Hub wants to handle less, it is up to him/her. Once a Hub has 10 individual Nodes under him/her, when adding a new member the Area Host will first ask that existing Hub if he/she can handle another Node. If not, the Area Host will be responsible for assigning a Hub position to one of the existing members of the net. If a Hub has fewer than 9 Nodes, but feels he/she cannot handle any more, it will be up to him/her to notify the Area Host so that when a new member is added, he/she will be assigned to a different Hub. ╓╖ ╓╖ ╟╨─────────────╨╢ ║ Area Hosts. ║ ╙───────────────╜ Ideally, each Area will comprise an entire Area Code. But, if an Area Host feels that his/her Area is getting to be too much to handle, he/she will then need to contact the Net Coordinator and then the Net Coordinator will decide how to break down the Area and will assign another Area Host for the resulting new Area. Area Hosts will be marked on the nodelist by the word HOST in front of there BBS info. For Example Toby Moore of Ft Worth Texas' info, who is the Fort Worth Texas area Host, will look like: HOST,2120,Ft_Worth_Area,,Ft_Worth_Tx,Toby_Moore,etc..etc.. In addition to the above responsibilities, the Area Host will also act as a Mail Hub to all the Hubs in his/Her area, as well as being responsible for updating and Maintaining his/her nodelist segment for that area. The last responsibility is to send all APP's to the AMM via normal routes. ╓───────────────────────────╖ ║Zones within Linear Network║ ╙───────────────────────────╜ The largest subdivision of the Linear Network is the "Zone". As of this date, there is one Zone within Linear Network. It is Zone 121 (North America). ╓─────────────────╖ ║ Headquarters. ║ ╙─────────────────╜ The "Headquarters" of Linear Network is based at RabbitLand II in Dallas Texas, where this net was founded and started. ╓───────────╖ ╓────────────╖ ╟───────────╨──────────╨────────────╢ ║ Positions in the National Council ║ ╙───────────────────────────────────╜ Elections are held once every 6 months in the Linear Network, if you think you or someone else in the Network can do a Better job then the Person Currently holding the Position, You can nominate yourself, or the Other person as soon as the Election is announced in the LINE_SYS echo. Each position has it's own responsibilities. At the announcement of elections the Voting will go in this order: 1st - 10th : Nominations for all positions 11th - 25th : Voting Via Private Netmail or in the LINE_SYS echo 26th - 30th : Announcements and Placing of the new Council If no one runs for a position, the current holder will be asked keep the position for another term. If the current holder of that position chooses to decline, the founders will appoint a pro temp to handle the position until the next election. ╓────────────────────────────────────────────────╖ ║ Checks and Balances with in the Linear Network ║ ╙────────────────────────────────────────────────╜ The Linear Network uses a unique Check and Balance system. This system is designed to keep power away from one person and given to the net in general. Any member of the council can be brought up on impeachment by any other member of council or any of the founders. The impeachment will then be determined and voted upon by the council members, area hosts, and Hubs. This will take place in the LINE_ADMIN echo. ╓───────────────────╖ ║Network Coordinator║ ╙───────────────────╜ The (NC) is the Voice of the Network. The NC will have full control over the Network as long as the policies are followed. The NC is responsible for keeping this Network together and running smoothly. ╓╖ ╓╖ ╟╨─────────────────────────╨╢ ║ National Echo Coordinator║ ╟╥─────────────────────────╥╢ ╙╜ ╙╜ The (NEC) is the NC's Helper. If the NC has a Question that he/she is unsure about the NC will ASK the NEC what He/She thinks About it. The NEC is also to be ready to be Moved into the NC's position in case of "Down Time" or impeachment. The (NEC) is the one person in charge of getting the echo's started, collecting ideas for new echo's, and, putting a Moderator in charge of the said echo. As well the NEC is also responsible in getting an Updated copy of the Echo.lst to the Network Coordinator in time to get out with the LINAPP.ZIP. The NEC will also Hatch out the Linnet.NA when changes are made. IE: Echos added / Removed ╓──────────────────────╖ ║ Public Relations ║ ╙──────────────────────╜ The (NPR) is more or less the voice of the Linear Network within Networks. He/She is responsible for helping the NC to Answer questions asked about the Linear Network by new App's, and Helping to handle arguments that may break out between nodes/hosts in the Network. ╓───────────────────────────╖ ║ Advertisement Coordinator ║ ╙───────────────────────────╜ The NAC is the person that helps spread the LinApp's around to BBS's that Might take an interest in the net. All Host's are expected to do this there area, But the NAC is the one that is always on the look out for new area hosts to join in the Gaming and Message area's. ╓────────────────────╖ ║ Gaming Coordinator ║ ╙────────────────────╜ The (NGC) is responsible to make sure that All nodes are running the inter BBS games fair, and legal according to the rules of the individual game. Also he/she will keep all nodes informed upon any NEW game that has come to there attention, either by Hatching it out in the LIN_DOOR file bone, or announcing it in the LINE_SYS echo. The NGC will be knowable in the setting up games and ready to help any node set up a door to the best of his/her ability. ╓─────────────╖ ║ ANSI Artist ║ ╙─────────────╜ The Ansi Artist is a individual with an expert "Art" ability to help with the advertisement of the net and it's individual nodes. He/She will Help with the drawing of LOGO.ANS if he/her has the time. The Ansi Artist will also be responsible in the Maintaining and "Upgrading" of the LINEAR.ANS. ╓──────────────────────╖ ║ Nodelist Coordinator ║ ╙──────────────────────╜ The Nodelist Coordinator (NNC) is responsible for making changes in the Nodelist as he/she sees fit. The NNC is also responsible for adding Zone's and giving them Numbers when needed. The NNC will maintain all apps received for the network and Make sure that The NC has a copy. He/She will also be responsible in adding Nodes to the nodelist when the Hub has given them a Node number,and hatching the Nodelist to the NC (or just Sending) for hatching out to the Network. The nodelist will be Hatched on Fridays and Ticked out to hubs as well. ╓╥──────────────────────────────╥╖ ╟╢ How New Members are Added. ╟╢ ╙╨──────────────────────────────╨╜ Although this is mentioned in other previous Sections of this document, I will reiterate in order to make this clear. The Sysop who wishes to join will obtain a copy of the information/ application packet LINAPP.ZIP (from either a Mail Hub, Area Host, Regional Host, the Net Coordinator, or anyone else who happens to have this file on his/her BBS.) The Sysop will then read over the files in the packet and complete the LINAPP.LIN file, filling in his/her information correctly, then saving the file using their last name with .LIN extension. The Sysop will then submit this application file in one of the following ways: A) Upload and/or Netmail this *.LIN file to either a Mail Hub, Area Host, Regional Host, or directly to the Net Coordinator. B) If the *.LIN file is received by a Mail Hub, he/she will then forward it to his/her Area Host (who may also be a Regional Host). This Area Host will be responsible for assigning the new member a Mail Hub and making the "addition" file (described above in Section "Area Hosts") and then sending it on to the Net Coordinator (along with the original APP file). C) If the *.LIN file is sent directly to the Net Coordinator, the Net Coordinator will Forward the App to the Nodelist Coordinator. As soon as the new nodelist is received by the new member's Mail Hub, the Mail Hub will be responsible for contacting the new member and helping him/her get the net set up on his/her BBS (as described above in Section "Mail Hubs". ╓╖ ╓╖ ╓╖ ╟╨──────────────────╨╨────────────────────╨╢ ║ How to Get Nodelist Information Changed. ║ ╙──────────────────────────────────────────╜ Each individual Node Sysop will be responsible for notifying his/ her Mail Hub of any information which needs to be changed in his/her nodelist listing (i.e., BBS name change, phone number change, modem changes). The Mail Hub will in turn notify his/her Area Host, who will route the Information to the Nodelist Coordinator. Also, if the individual Node's BBS will be "Down" for either a short or extended period of time, he/she will also need to notify his/ her Mail Hub. If the BBS will be Down for only a short time (less than 2 or 3 weeks) the Mail Hub will simply put the Node's mail on "Hold" for that time. If the BBS will be Down for an extended or indefinite period of time, the Mail Hub will notify the Nodelist Coord., who will make this notation to his/her weekly "addition" file, which will eventually be received by the Net Coordinator who will add the "Down" flag to that individual Node's listing. If for any reason the individual Node's Sysop decides to leave the Net, he/she will contact his/her Mail Hub, who will in turn contact his/her Area Host, and so on (as described above in this Section). ╒════════════════════════╕ │ Policies about Echoes │ ╘════════════════════════╛ -╓─────────╖- ║ECHO MAIL║ -╙─────────╜- These message areas are optional and no one is required to carry them with 1 exception. All BBS's must carry LIN_SYSOP . That is the only 1 that is required. Also Regional Hosts/Hubs are required to carry LIN_ADMIN and are requested to carry all echoes if possible. Whenever echoes are added/changed/deleted, all Regional Hosts, Area Hosts, and Mail Hubs will be notified of the changes. ╓─────────────────────────╖ ║ Rules of the Echoes. ║ ╙─────────────────────────╜ ALL Linear Network echoes must abide by a basic set of rules, as listed below: A) Vulgar language and/or abusive behavior toward any other person will not be tolerated. A polite warning for the first offense, but the Moderator will be required to prevent it from happening further. B) Discussion must stay on-topic. The Echo Moderator is expected to allow a little deviation, but the conference as a whole must represent the topic for the echo. C) When a Topic is considered "Off-Topic" in an Echo, the Moderator of that echo will first give a polite Public message, second give a polite Netmail Message asking that the SysOp of the Said BBS will attempt to put an end to the topic, and 3rd will turn off the BBS for one Week from that echo. Any offenses after that will result in a "Permanent" ban from the Echo. Moderators are the "President" of the echos. They are in charge of the echo that they have been asked to moderate. If there is a Problem with Said moderator, Please Bring it to the attention of the NEC or the NC Via Netmail. ╓──────────────────────────────────────╖ ║Handles and Aliases in Linear Network.║ ╙──────────────────────────────────────╜ Only Echoes in Linear Network marked in the ECHO.LST to allow aliases will allow handles/aliases to be used. This does not mean that BBS's must allow handles. Sysop's are free to decide if their users can use handles or not. Handles or Aliases must not be vulgar or racial in any way. There are plenty of names that can be used without a need for these types. [End of Network Guidelines] UPDATES: ──────── 2/15/95 : Policies were written and Sent to Co-Founder Toby Moore for Proof-Reading 2/21/95 : Found Small errors with file names Made Changes 7/20/95 : Yet another Spell Check. Separated NEC & NEM 11/21/95: Removed all References to the NEM. Added References to the Automated Mail Machine. Removed Support Sites. 12/08/95: Added that this Doc can Change. More AMM reference. Fee's for downlinks. MakeNL & Sending Apps to AMM for Hosts. Took all references to ANC changed to NEC. Added in Advertising Coord. Added in Ansi to the Policy. 3/25/96 : Added in the check and Balance statements. Minor corrections in wording. Hubs have to have AT LEAST a 14.4. Took out all references to LIN_APP.ZIP